Methods for authenticating user access to a scanned document on a cloud-based server

ABSTRACT

A cloud-based server and a port monitor on a device provide authentication of a user to access scanned documents on the server. A scanning device may capture a digital image of a document. The port monitor uploads data for a scanned document to the cloud-based server. Once the data for the document is uploaded, a claim code is generated by the cloud-based server. The port monitor receives the claim code. The port monitor initiates the launch of a browser having a uniform resource locator (URL) address for the server along with the claim code. The user is authenticated using a login page and the claim code associated to the user to allow access to the document on the server.

FIELD OF THE INVENTION

The present invention relates to authenticating printing operations froma cloud-based server. More particularly, the present invention relatesto authenticating user access to a scanned document at the cloud-basedserver.

DESCRIPTION OF THE RELATED ART

A user should be authenticated prior to submitting a scanned document toa cloud-based server. The authentication determines its permission. Italso allows the server to identify the user of a print job, or otherprocessing instruction, being submitted. Authentication usually requiresa client program to prompt the user to enter its username and passwordin a login dialog. Most client applications have no problem prompting alogin dialog authenticate a user to a server, then submitting thescanned document to the cloud-based server. Other client applications,such as a port monitor, may find it difficult to show a login boxbecause authentication using the application interferes with the normalprinting flow.

SUMMARY OF THE INVENTION

A method for authenticating user access to a scanned document at acloud-based server is disclosed. The method includes scanning a documentat a device on a network. The method also includes uploading data forthe scanned document to the cloud-based server from a port monitor. Themethod also includes generating a claim code by the cloud-based server.The method also includes providing the claim code to the port monitor.The method also includes launching a browser with a uniform resourcelocator (URL) address indicating the cloud-based server. The URL addressincludes the claim code. The method also includes assigning the claimcode to a user session initiated by the browser. The method alsoincludes selecting the scanned document associated with the claim codeto be sent from the cloud-based server.

A method for authenticating user access to a scanned document at acloud-based server is disclosed. The method includes uploading data fromthe scanned document to the cloud-based server. The method also includesreceiving a first uniform resource locator (URL) address at a portmonitor. The first URL address refer to the scanned document stored onthe cloud-based server. The method also includes submitting a request toaccess the scanned document using the first URL address. The requestincludes document metadata information for the scanned document. Themethod also includes generating a claim code for the scanned document atthe cloud-based server. The method also includes receiving the claimcode at the port monitor. The method also includes forwarding the claimcode to the cloud-based server using a second URL address. The methodalso includes authenticating a user session to access the scanneddocument according to the claim code. The method also includesforwarding the scanned document to a device from the cloud-based server.

A method for authenticating a user session to access a scanned documenton a cloud-based server is disclosed. The method includes uploading datafor the scanned document to the cloud-based server using a port monitor.The method also includes submitting the scanned document includingdocument information metadata. The data and document informationmetadata for the scanned document is stored on the cloud-based server.The method also includes generating a claim code at the cloud-basedserver. The method also includes providing the claim code to the portmonitor. The method also includes forwarding the claim code using auniform resource locator (URL) address initiated in a browser by theport monitor to the cloud-based server. The method also includesdetermining whether the user information associated with the claim codeis valid. The method also includes establishing the user session oncethe user information is validated. The method also includes selectingthe scanned document on the cloud-based server.

BRIEF DESCRIPTION OF THE DRAWINGS

Various other features and attendant advantages of the present inventionwill be more fully appreciated when considered in conjunction with theaccompanying drawings.

FIG. 1A illustrates a system to print using a cloud-based serveraccording to the disclosed embodiments.

FIG. 1B illustrates a device having a port monitor to print using thecloud-based server according to the disclosed embodiments.

FIG. 2 illustrates a block diagram of components of the printing deviceused in conjunction with the authentication system according to thedisclosed embodiments.

FIG. 3 illustrates a flowchart for uploading data for a scanned documentto the cloud-based server according to the disclosed embodiments.

FIG. 4 illustrates a flowchart for providing a claim code for theuploaded scanned document according to the disclosed embodiments.

FIG. 5 illustrates a flowchart for authenticating user to access thescanned document from the cloud-based server according to the disclosedembodiments.

FIG. 6 illustrates a block diagram of a login page within a browser toauthenticate a user according to the disclosed embodiments.

FIG. 7 illustrates a flowchart for authenticating user to access thescanned document from the cloud-based server using an authenticationtoken according to the disclosed embodiments.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference will now be made in detail to specific embodiments of thepresent invention. Examples of these embodiments are illustrated in theaccompanying drawings. Numerous specific details are set forth in orderto provide a thorough understanding of the present invention. While theembodiments will be described in conjunction with the drawings, it willbe understood that the following description is not intended to limitthe present invention to any one embodiment. On the contrary, thefollowing description is intended to cover alternatives, modifications,and equivalents as may be included within the spirit and scope of theappended claims. Numerous specific details are set forth in order toprovide a thorough understanding of the present invention.

A user submits a scanned document to a cloud-based server, authenticatesuser access to the scanned document, and then claims the scanneddocument later for printing or other operations. Once the user submitsthe scanned document, a claim code is provided that is not associatedwith a user. The claim code is presented to claim the scanned documentstored on a cloud-based server. Most applications authenticate the userfirst then do printing operations. The disclosed embodiments do not wantto stop printing to wait for authentication. Instead, the printingprocess continues without interruption. Authentication may be done on awebsite, which may be difficult for a printing application to do.Printing application does not need a user interface to authenticate.

The disclosed embodiments minimize printing flow interruption byallowing a client application to submit a scanned document for printingoperations even without prior authentication. This feature works byissuing a claim code to the submitted scanned document or other printingoperation, thereby redirecting the user to a web application to performpost authentication. The scanned document is associated to theauthenticated user identified by the claim code. This process isbeneficial because it minimizes and simplifies implementation efforts inclient programs. The disclosed embodiments also reduce developmentcomplexity of the application because authentication is offloaded to abrowser. Application does not need updating if authentication protocolvia the browser is updated.

The disclosed system and associated methods provide the ability tosupport possible upload modes. One mode may be a pass-through mode.Another mode may be a buffered mode. It also allows uninterruptedprinting flow for a printing application, such as Windows Port Monitor™.A unique claim code is used to identify a submitted scanned document. Abrowser is launched to claim a document either by a previouslyauthenticated user or with a new authentication. Unclaimed scanneddocuments expire after certain conditions are met along with datacleanup to avoid orphaned documents for security and storageconsideration purposes. The disclosed processes do not let scanneddocuments stay in limbo but may require them to be claimed after acertain point.

Although a scanned document, print job, or a job is discussed herein,the disclosed embodiments may pertain to any type of operationsperformed on a printing device. These operations include copying,scanning, storing of documents, editing documents, faxing, and the like.The user wishes to send a document, as data, to another device from thecloud-based server and to authenticate the access to that document. Thedisclosed embodiments may refer to the data for the document as ascanned document, print job, or job.

A scanning device according to the disclosed embodiments may continuescanning other documents along with associated processing withoutinterruption during the printing process. Instead of waiting for userauthentication to access a scanned document, the disclosed embodimentsrelease the scanning device and an associated port monitor to performadditional operations while authentication occurs. The scanned documentmay be sent to the cloud-based server to await authorization. Thescanning device does not need to store the scanned document in order toprint.

FIG. 1A depicts a system 100 to print using a cloud-based server 110according to the disclosed embodiments. FIG. 1B depicts a device 102having a port monitor 108 to print to the cloud-based server accordingto the disclosed embodiments. FIG. 1B shows the components that may beutilized for printing within system 100. System 100 may include anetwork that connects the various components shown. This network may bea wireless or wired network as well as a local area network (LAN) orwide area network (WAN). The various components in system 100 mayinclude internet protocol (IP) addresses that uniquely identify thecomponents within the network so that information may be exchanged.Preferably, any network within system 100 is a secure network. A usershould be authenticated before using any component within system 100 oraccessing data or information from such component.

System 100 includes device 102 connected to cloud-based server 110 overa network. System 100 also includes printing device 104, which receivesscanned documents or print jobs from cloud-based server 110 as well asdirectly from device 102. System 100 also may include other componentsto perform printing and scanning operations. System 100 may include aplurality of devices 102 and printing devices 104 that interact withserver 110.

Device 102 may be a computing device, such as a computer, mobile tablet,mobile device, laptop, another server, and the like. The features ofdevice 102 are disclosed in greater detail below. Device 102 printswithin system 100 using port monitor 108. Port monitor 108 is a printingsubsystem that passes raw scan data 109 from spooler 138 to a printingdevice 104. In some embodiments, port monitor 108 uploads raw scan data109 to cloud-based server 110.

Scanning device 101 may be connected to device 102. In some embodiments,scanning device 101 may be part of device 102. FIG. 1A shows scanningdevice 101 as a separate component within system 100 while FIG. 1B showsscanning device 101 as a component within device 102. Scanning device101 captures images of a document to generate an electronic file 1011that is provided to device 102. Scanning device 101 may be a scanner, acamera, or any device that can capture images of a document. Documentmay include documents with text, graphics, photos, charts, and otherinformation, or any combination thereof. Scanning device 101 generateselectronic file 1011 based on the document. Text and graphicalrepresentations within the document are represented by the data withinelectronic file 1011.

Scanning device 101 may be a flatbed scanner, a hand-held scanner, awand scanner, a mechanically driven scanner, a drum scanner, anon-contact planetary scanner, a three-dimensional (3D) scanner, adigital camera, an application executed on a device, such as device 102,and the like. Scanning device 101 may use a uniform interface tocommunicate with device 102 or the components disclosed in FIGS. 1A and1B. The scanned output may be a non-compressed image. Scanning device101 also may use optical character recognition (OCR) programs togenerate an output file.

Cloud-based server 110 preferably is a secure or private server suchthat one need to be authenticated before accessing data thereon. Priorto accessing a scanned document to cloud-based server 110, a user firstmust be authenticated to determine its permission to access the server.Server 110 should identify the owner of the print job being submitted.Authentication may require a process to prompt the user to enter his/herusername, password, personal identification number (PIN), or other suchprivate information. The disclosed embodiments provide such processes toauthenticate the user without printing flow interruption.

Components on cloud-based server 110 include file service module 112that receives uploaded raw scan data 109 from port monitor 108 over thenetwork. Port monitor 108 may initiate a job submission request toserver 110. Port monitor 108 then may upload raw scan data 109 to fileservice module 112. File service module 112 may generate and send aunique access uniform resource locator (URL) address 111 to port monitor108. URL address 111 is used as a reference to the just uploaded scandata.

Cloud-based server 110 also includes job service module 114. Job servicemodule 114 receives a request for scanned document 113 which alsoincludes scan metadata information 115. Scan metadata information 115may include details about the scanned document such as document name,file name, file size, encoding type, content type, document type,timestamps, and the like. Cloud-based server 110 through job servicemodule 114 issues a unique claim code 117 for scanned document 113 andsaves this information in database 118. Claim code 117 also is providedto port monitor 108.

Authentication service module 116 of cloud-based server 110 acts inconjunction with port monitor 108 and internet browser 119 toauthenticate the user before sending scanned document 113 to printingdevice 104. Port monitor 108 initiates a redirection from device 102 tolaunch browser 119 by passing along claim code 117 in a URL address 121.Claim code URL address 121 points to cloud-based server 110.Authentication service module 116 interacts with browser to obtain userinformation 120. Authentication service module 116 assigns claim code117 to that user presenting user information 120. The user will now seescanned document 113 in his/her scan list, such as displayed on device102.

The user may instruct that cloud-based server 110 submit scanneddocument 113 to printing device 104. Printing device 104 may be amulti-functional printing device in that it may print, copy, scan, edit,fax, store, and modify a document or documents. Printing device 104 alsoincludes engine 106 that helps complete these functions. Printing device104 and engine 106 are disclosed in greater detail below.

The processes associated with port monitor 108, cloud-based server 110,and printing device 104 are disclosed in greater detail below. Referringto FIG. 1B, a block diagram of device 102 is shown. Device 102 may be adata processing apparatus that includes components that are enabled by aprocessor 130 executing a program loaded from a memory 129. Memory 129may have a location within device 102. Preferably, memory 129 is arandom access memory (RAM) within device 102. The program may be loadedinto memory 129 from another location or device.

Operating system 130 operates on device 102. Operating system 130 mayinteract with processor 131 to launch application 132 and enable thecomponents for printing shown in FIG. 1B. Application 132 may besoftware instructions that are loaded onto processor 130 from memory 129to convert device 102 into a special purpose machine. Alternatively,application 132 may run on device 102 with other programs. Application132 may be invoked by the user. In some embodiments, application 132includes a word processor and an image processing function. Application132 creates processed data by processing data, which is stored in memory129 or other memory in response to a user instruction. If the user wantsto print the processed data created by the execution of application 132,then the user may launch a graphical user interface (GUI) using display146 to display a print wizard or other information capture interface,such as detecting gestures or speech, in order to select a command toprint. Other commands may include one to scan or send the processed datato another device or location within system 100.

Device 102 also may include scanning device 101. Scanning device 101 maybe an image scanner that scans or captures images, printed text, andother objects to convert these items to a digital image, or electronicfile 1011. In some embodiments, electronic file 1011 may includenon-compressed images of the document. Electronic file 1011 may beprovided to application 132 for editing and processing, as disclosedabove. Application 132 may generate scanned document 113 through theseactions. Electronic file 1011 may be opened as a document by application132. Alternatively, application 132 may be skipped and electronic file1011 becomes the scanned document provided to port monitor 108, asdisclosed below, without any edits. In some embodiments, device 102 isscanning device 101 such that other operations are not performed exceptfor capturing images of the document. Word processing features may bebypassed.

Device 102 includes a network interface 142 and an input/output (I/O)interface 144. Network interface 142 receives data based on a TCP/IPprotocol or the like through the network of system 100. Networkinterface 142 also outputs print data or processed data processed bydevice 102 through the network of system 100. Network interface 142 mayuse input connection 142 i and output connection 142 o to communicateover system 100.

I/O interface 144 receives an input from an inputting device, such as akeyboard, touch screen, heads up display, motion or speech detector,mouse, and the like. I/O interface 144 may send data and instructionssuch as an event notification to application 132. I/O interface 144 maycause display 146 to display a result of execution of application 132via a graphics driver or the like in order to provide the GUI to captureinstructions and commands from the user. I/O interface 144 may use inputconnection 144 i and output connection 144 o to perform these functions.

When a print or scan command is issued, an instance of a formatconverting part is generated. The print data is created with a formatacceptable to a printing device, such as printing device 104. The printdata also may be compatible with specifications set forth by cloud-basedserver 110 or system 100. The format converting part of device 102 mayinclude drawing component 134 and print processor 140. For example, theformat converting part may contain a graphics display interface (GDI).If the user issues a print command of the processed data throughapplication 132, then the format converting part calls drawing component134 to create an instance of a drawing component contained in theprocessed data. The user also may issue a print command through scanningdevice 101.

Drawing component 134 may send a format specific to an application suchas image metadata to print processor 140 in order to change the formatinto a specific format including raster data, which may be used byprinting device 104. In some embodiments, the data structure may beregistered as a data structure for registering a data value associatedwith drawing data and a data structure for registering a data value foran external transmission.

In some embodiments, text contained in the processed data is sent toprinter driver 136 together with the setting of the font and otherinformation. Printer driver 136 performs processing such as setting of atext character, setting of a line interval and a character interval,setting of margins, setting of a text arrangement area and the like inorder to create a format specific to printing device 104. Printer driver136 may generate print data in order to further control printing device104 by describing the page description language (PDL) or printer joblanguage (PJL) in the page description language describing area withrespect to image data and the text during and after the disclosedprocessing.

In order to generate the print data of a format specific to printingdevice 104, printer driver 136 sends the created print data to spooler138 so that the spooler transfer the data being processed to the formatconverting part through print processor 140. The data is output fromdevice 102 via spooler 138 and port monitor 108 after completion ofcreation of the print data, as shown by job raw data 109.

Port monitor 108 sends out the print data, or raw data 109, inaccordance with an output destination. Port monitor 108 acquires, fromthe described data structure, output destination information such as anIP address or a host name of another device within system 100, such asprinting device 104 or cloud-based server 110. Raw print data 109 issent to this location through network interface 142. In someembodiments, port monitor 108 may use buffer 141 to store the processeddata until it is ready to be uploaded over system 100. Port monitor 108also may request printing or other operations on printing device 104.

In some embodiments, scanning device 101 may include port monitor 108.Print processing operations are not performed on the scanned image orimages of the document. Raw data 109 is the data captured by scanningdevice 101. This data is provided to port monitor 108 when printingusing cloud-based server 110.

In summary, the disclosed embodiments, application 132 is invoked by theuser to create or edit a scanned document or other file. In turn, datais created and processed for the document. If the user instructsprinting of the data, then printer driver 136 receives a specific unitof data from application 132. The data is used for the requested scanneddocument. Printer driver 136 sequentially generates a PDL image forevery specific unit of data. The generated PDL image is passed tospooler 138. Port monitor 108 sequentially receives the scanneddocument, which may be the PDL image, from spooler 138. Port monitor 108sets up a port in which to transfer scan raw data 109 for the scanneddocument to a component on system 100.

FIG. 2 illustrates a block diagram of components of printing device 104used in conjunction with system 100 according to the disclosedembodiments. The architecture shown in FIG. 2 may apply to anymulti-functional printer or image forming apparatus that scans documentsto perform other functions, such as printing, storing, copying, and thelike. As disclosed above, printing device 104 may send and receive datafrom device 102 through port monitor 108 or cloud-based server 110.

Printing device 104 includes a computing platform 201 that performsoperations to support these functions. Computing platform 201 includes acomputer processing unit (CPU) 202, an image forming unit 204, a memoryunit 206, and a network communication interface 210. Other componentsmay be included but are not shown for brevity. Printing device 104,using computing platform 201, may be configured to perform variousoperations, such as scanning, copying, printing, receiving or sending afacsimile, or document processing. As such, printing 104 may be aprinting device or a multi-function peripheral including a scanner, andone or more functions of a copier, a facsimile device, and a printer. Toprovide these functions, printing device 104 includes printer components220 to perform printing operations, copier components 222 to performcopying operations, scanner components 224 to perform scanningoperations, and facsimile components 226 to receive and send facsimiledocuments. CPU 202 may issue instructions to these components to performthe desired operations.

Printing device 104 also includes a finisher 211 and one or more papercassettes 212. Finisher 211 includes rotatable downstream rollers tomove papers with an image formed surface after the desired operation toa tray. Finisher 211 also may perform additional actions, such assorting the finished papers, binding sheets of papers with staples,doubling, creasing, punching holes, folding, and the like. Papercassettes 212 supply paper to image the various components 220, 222,224, and 226 to create the image formed surfaces on the papers. Papercassettes 212 may include papers having various sizes, colors,composition, and the like. Paper cassettes 212 may be removed to refillas needed.

Document processor input feeder tray 230 may be the physical componentsof printing device 104 to receive papers and documents to be processed.A document is placed on or in document processor input feeder tray 230,which moves the document to other components within printing device 104.The movement of the document from document processor input feeder tray230 may be controlled by the instructions input by the user. Forexample, the document may move to a scanner flatbed for scanningoperations. Thus, document processor input feeder tray 230 provides thedocument to scanner components 220. As shown in FIG. 2, documentprocessor input feeder tray 230 may interact with engine firmware 106 toperform the desired operations.

Memory unit 206 includes memory storage locations 214 to storeinstructions 215. Instructions 215 are executable on CPU 202 or otherprocessors associated with printing device 104, such as any processorswithin components 220, 222, 224, or 226. Memory unit 206 also may storeinformation for various programs and applications, as well as dataspecific to printing device 104. For example, a storage location 214 mayinclude data for running an operating system executed by computingplatform 201 to support the components within printing device 104.According to the disclosed embodiments, memory unit 206 may store thetokens and codes used in performing the authentication operations forprinting device 104.

Memory unit 206 may comprise volatile and non-volatile memory. Volatilememory may include random access memory (RAM). Examples of non-volatilememory may include read-only memory (ROM), flash memory, electricallyerasable programmable read-only memory (EEPROM), digital tape, a harddisk drive (HDD), or a solid-state drive (SSD). Memory unit 206 alsoincludes any combination of readable or writable volatile memories ornon-volatile memories, along with other possible memory devices.

Computing platform 201 may host one or more processors, such as CPU 202.These processors are capable of executing instructions 215 stored at oneor more storage locations 214. By executing these instructions, theprocessors cause printing device 104 to perform various operations. Theprocessors also may incorporate processing units for specific purposes,such as application-specific integrated circuits (ASICs) and fieldprogrammable gate arrays (FPGAs). Other processors may be included forexecuting operations particular to components 220, 222, 224, and 226. Inother words, the particular processors may cause printing device 104 toact as a printer, copier, scanner, and a facsimile device.

Printing device 104 also includes an operations panel 208, which may beconnected to computing platform 201. Operations panel 208 may include adisplay unit 216 and an input unit 217 for facilitating interaction witha user to provide commands to printing device 104. Display unit 216 maybe any electronic video display, such as a liquid crystal display (LCD).Input unit 217 may include any combination of devices that allow usersto input information into operations panel 208, such as buttons, a touchscreen, a keyboard or keypad, switches, dials, and the like. Preferably,input unit 217 includes a touch-screen digitizer overlaid onto displayunit 216 that senses touch to receive inputs from the user. By thismanner, the user interacts with display unit 216.

Printing device 104 also includes network communication processing unit218. Network communication processing unit 218 may establish a networkcommunication, such as a wireless or wired connection with one or moreother image forming apparatuses and a server in an image forming system.CPU 202 may instruct network communication processing unit 218 totransmit or retrieve information over a network using networkcommunication interface 210. As data is received at computing platform201 over a network, network communication processing unit 218 decodesthe incoming packets and delivers them to CPU 202. CPU 202 may actaccordingly by causing operations to occur on printing device 104. CPU202 also may retrieve information stored in memory unit 206, such assettings for printing device 104.

Printing device 104 also includes engine 106. Engine 106 may be acombination of hardware, firmware, or software components that actaccordingly to accomplish a task. For example, engine 106 is comprisedof the components and software to print a document. It may receiveinstructions from computing platform 201 after user input via operationspanel 208. Alternatively, engine 106 may receive instructions from otherattached or linked devices.

Engine 106 manages and operates the low-level mechanism of the printingdevice engine, such as hardware components that actuate placement oftoner onto paper. Engine 106 may manage and coordinate the half-toner,toner cartridges, rollers, schedulers, storage, input/output operations,and the like. Raster image processor (RIP) firmware 290 that interpretsthe page description languages (PDLs) may transmit and send instructionsdown to the lower-level engine 106 for actual rendering of an image andapplication of the toner onto paper during operations on printing device104.

FIG. 3 depicts a flowchart 300 for uploading data for a scanned document113 to cloud-based server 110 according to the disclosed embodiments.The disclosure of flowchart 300 may refer to elements of FIGS. 1A, 1B,and 2 in disclosing the features of FIG. 3. Flowchart 300, however, isnot limited to the embodiments disclosed by FIGS. 1A, 1B, and 2.

Step 301 executes by scanning a document at scanning device 101. Asdisclosed above, scanning device 101 may generate electronic file 1011.Scanning device 101 captures digital images of the contents of thedocument, such as text, graphics, pictures, and the like. In someembodiments, electronic file 1011 may not be compressed or processed.

Step 302 executes by opening electronic file 1011 as a document inapplication 132 on device 102. As disclosed above, data may begenerated, modified, or processed within the document. For example, auser may enter text or images into the document. Application 132 may bea word processing application, spreadsheet, and the like. In someembodiments, application 132 may be an OCR application that convertsgraphical images of text into standard text that may be edited. Step 304executes by initiating printing or other operations of the document fromdevice 102. The user may initiate printing by entering commands or byselecting options from a menu. Step 306 executes by starting theprinting process within device 102. As disclosed above, printer driver136, spooler 138, and other components generate the raw data for thescanned document.

Step 308 executes by receiving the print request at port monitor 108.Port monitor 108 may perform any necessary internal processing includingidentifying a destination for the scanned document for the document. Insome embodiments, the print operations may be completed usingcloud-based server 110. Scanned document 113, may be stored oncloud-based server 110 and then forwarded to printing device 104.Alternatively, port monitor 108 may identify printing device 104 toreceive the scanned document.

Step 310 executes by initiating a job submission request from portmonitor 108. Step 312 executes by submitting the job submission requestto cloud-based server 110. Port monitor 108 may initiate and submit thejob submission request to server 110 by calling its application programinterfaces (APIs) to interface with the server.

Step 314 executes by determining whether the raw data from port monitor108 is to be buffered. In some embodiments, the data for the entirescanned document are collected before upload to cloud-based server 110.If yes, then step 315 executes by buffering raw data 109 in buffer 141as it comes from port monitor 108. Port monitor 108 may be instructed toenter a buffered mode that collects the data in buffer 141. Flowchart300 then proceeds to step 316, disclosed below.

If step 314 is no, then flowchart 300 proceeds directly to step 316. Ifthe buffered mode is not used, then a pass-through mode is used so thatraw data 109 are directly uploaded to cloud-based server 110 using astreaming or chunk-by-chunk method. Before being uploaded, step 316executes by applying data processing to raw data 109 before it leavesnetwork interface 142. Data processing operations include compression,encryption, encoding, signing, and the like that are applied to thedata. In some embodiments, step 316 may be optional in that raw data 109is streamed directly from network interface 142 without any processing.

Step 318 executes by uploading raw data 109 to cloud-based server 110.The data are uploaded using file service module 112. File service module112 receives raw data 109 within cloud-based server 110. In someembodiments, file service module 112 may buffer the received data untilthe upload is complete. It also may apply data processing operations onthe received data to decode, decrypt, and the like.

Step 320 executes by completing the upload operations for raw data 109.An indication that the data transfer is complete may be received at fileservice module 112. Step 322 executes by issuing an access URL address111. Access URL address 111 may be a unique access URL address toreference the raw data just uploaded from device 102. Access URL address111 also may be known as the upload URL address. Step 324 executes byreceiving access URL address 111 at port monitor 108. Port monitor 108may keep access URL address 111 until scanned document 113 is ready tobe submitted to cloud-based server 110. Step 326 executes by storinguploaded raw data 109. In some embodiments, file service module 112 maystore the raw data on database 118.

FIG. 4 depicts a flowchart 400 for providing a claim code for theuploaded scanned document according to the disclosed embodiments. Thedisclosure of flowchart 400 may refer to elements of FIGS. 1A, 1B, and 2in disclosing the features of FIG. 4. Flowchart 400, however, is notlimited to the embodiments disclosed by FIGS. 1A, 1B, and 2.

Step 402 executes by calling cloud-based server 110 using access URLaddress 111. Port monitor 108 may call another cloud-based printingsystem API using access URL address 111. Access URL address 111 directsthe communication interface to job service module 114. Step 404 executesby submitting scanned document 113 to job service module 114 along withdocument metadata information 115. Port monitor 108 submits documentmetadata information 115 to complete scanned document 113. Metadatainformation 115 may include details about the scanned document, or printjob, such as document or scan name, file name, file size, encoding type,content type, document type, timestamps, and the like. When associatedwith raw data 109, the data and information for scanned document 113 arecaptured at cloud-based server 110. Job service module 114 may use theunique URL address of access URL address 111 to identify the raw datauploaded for the scanned document.

Step 406 executes by generating claim code 117 for scanned document 113.Claim code 117 is a unique claim code associated with scanned document113. It identifies scanned document 113 from a plurality of scanneddocuments stored on cloud-based server 110. Claim code 117 may be in avariety of forms, including a random string, an integer form, auniversally unique identifier, and the like. In some embodiments,information provided by port monitor 108, such as metadata information115, may be used to generate claim code 117. Step 408 executes bystoring claim code 117 in database 118. Job service module 114 mayconfigure claim code 117 to identify scanned document 113 withindatabase 118.

Step 410 executes by forwarding claim code 117 to port monitor 108 usingthe communication interface between the port monitor and job servicemodule 114. Thus, claim code 117 is provided to port monitor 108 as wellas kept by cloud-based server 110. Step 412 executes by initiating aredirection from port monitor 108 from cloud-based server 110 to abrowser 119. Browser 119 may be located on device 102 and displayed ondisplay 146. Alternatively, browser 119 may be located on anotherdevice, such as an application on a mobile device. Port monitor 108 maysend a command to the application to enable browser 119.

Step 414 executes by launching browser 119. Step 416 executes bygenerating a claim code URL address 121 that includes claim code 117.Port monitor 108 passes along claim code 117 that is placed into claimcode URL address 121. Claim code URL address 121 points to cloud-basedserver 110. Thus, the claim code URL address directs a call to jobservice module 114 to set up the communication interface over system100.

For example, the URL address to cloud-based server 110 may behttps://jp.anytime-print.com/jobclais. The claim code may beaeb59781-89a3-4bd9-9361-4059aabe82d5. Thus, the claim code URL addressmay behttps://jp.anytime-print.com/jobclaims/aeb59781-89a3-4bd9-9361-4059aabe82d5.Port monitor 108 delivers claim code 117 with the URL to cloud-basedserver 110. Step 418 executes by completing operations at port monitor108. Port monitor 108 is not needed for further operations toauthenticate the user to access scanned document 113. It now maycommence additional scanning and printing operations for device 102.Cloud-based server 110 may release any resources associated withcommunicating with port monitor 108.

FIG. 5 depicts a flowchart 500 for authenticating user to access thescanned document at the cloud-based server according to the disclosedembodiments. The disclosure of flowchart 500 may refer to elements ofFIGS. 1A, 1B, 2, and 6 in disclosing the features of FIG. 5. Flowchart500, however, is not limited to the embodiments disclosed by FIGS. 1A,1B, 2, and 6.

Step 502 executes by calling to cloud-based server 110 using claim codeURL address 121 from browser 119. As disclosed in FIG. 4, claim code URLaddress 121 includes claim code 117. Step 504 executes by determiningwhether a valid and authentication user session already exists. If yes,then flowchart 500 proceeds to step 522, disclosed below. If step 504 isno, then step 506 executes by redirecting browser 119 to a login page.Browser 119 also calls to authentication service module 116 to initiatethe authentication process for the user.

Step 508 executes by displaying the login page to authenticate a userfor a session to access scanned document 113 at cloud-based server 110.An example of a login page 602 within browser 119 may be disclosed byFIG. 6. FIG. 6 depicts a block diagram of a login page 602 within abrowser 119 to authenticate a user according to the disclosedembodiments. Information entered into browser 119 may be sent tocloud-based server 110. Job service module 114 may pass control of theauthentication process to authentication service module 116 at thispoint. The URL address for the login page, or URL address 603, maydiffer from the previous URL addresses used to upload the scanneddocument and present claim code 117 to cloud-based server 110.

Step 510 executes by entering user information 120 for the user ontologin page 602. For example, username field 604 may receive the usernameand password field 606 may receive a password associated with theusername. Button 608 instructs browser 119 to send the user informationto authentication service module 116. Step 512 executes byauthenticating user information 120 with the credentials for the userstored on cloud-based server 110. Alternatively, authentication servicemodule 116 may confirm user information 120 with credentials located onanother device in system 100.

Step 514 executes by determining whether user information 120 is valid.If no, then step 516 executes by sending an alert to the user. The alertmay be sent to port monitor 108. Browser 119 may redirect the user backto login page 602. Further, claim code 117 is not claimed for print job113 by the user. Thus, it stays stored on server 110. After a conditionis met, claim code 117 may not be valid. Step 518 executes bydetermining whether a condition to delete claim code 117 is met. Acondition may include a predetermined period of time stored on server110, a number of unsuccessful attempts to authenticate the user, and thelike. If yes, step 520 executes by deleting claim code 117 along withrelated database entries and files from database 118. This data may bedeleted for security and storage allocation purposes. Cloud-based server110 does not want limited resources devoted to unclaimed scanneddocuments. If step 518 is no, then flowchart 500 proceeds back to step510.

If step 514 is yes, then the user is validated and successfullyauthenticated. Flowchart 500 proceeds to step 522. Step 522 executes byassigning claim code 117 to the user. Claim code 117 may be assigned tothe user session between the user and cloud-based server 110. Asdisclosed above, if a valid user session already exists when claim code117 is provided by claim code URL address 121, then the claim code isassigned to that session so that the user does not need to re-enter userinformation 120. Browser 119 may not be redirected to login page 602.

Step 524 executes by retrieving scanned document 113 on cloud-basedserver 110 using claim code 117. After successful association of claimcode 117 to the user, the user will see the scanned document in his/herscan list for scanned documents stored on the server. The scan list maybe displayed in browser 119. Step 526 executes by selecting scanneddocument 113 from the scan list. Step 528 executes by sending the datafor scanned document 113, including raw data 109, to printing device104. In some embodiments, cloud-based server 110 sends scanned document113 to printing device 104 such that application 132 is not involved inthe printing process after port monitor 108 is done. Application 132,scanning device 101, and port monitor 108 may be released to performother operations, including those not involving server 110 or printingdevice 104.

FIG. 7 depicts a flowchart 700 for authenticating user to access thescanned document from the cloud-based server using an authenticationtoken 616 according to the disclosed embodiments. The disclosure offlowchart 700 may refer to elements of FIGS. 1A, 1B, 2, and 6 indisclosing the features of FIG. 7. Flowchart 700, however, is notlimited to the embodiments disclosed by FIGS. 1A, 1B, 2, and 6.Flowchart 700 also may execute in conjunction with flowchart 500disclosed above.

Step 702 executes by determining that the user is not authenticatedafter receiving claim code 117 using claim code URL address 121, asdisclosed above. As disclosed by flowchart 500, if a valid andauthenticated user session exists, then authentication processes may notbe executed. One way to determine whether such a user session exists isto determine whether an authentication token 616 is associated with thesession. Authentication token 616 may indicate that the user informationis received and confirmed at cloud-based server 110.

Step 704 executes by generating authentication token 616 in order toauthenticate the user retrieving scanned document 113. Authenticationtoken 616 may be a string of data associated with the user or thissession to authenticate the user. Cloud-based server 110 generatesauthentication token 616. For example, authentication service module 116may generate authentication token 616 when browser 119 is redirected tologin page 602.

Step 706 executes by sending authentication token 616 to browser 119.Browser 119 already has claim code 117, as provided by port monitor 108.Step 708 executes by entering user information 120 using login page 602,as disclosed above. Step 710 executes by authenticating the user withuser information 120. In some embodiments, cloud-based server maygenerate authentication token 616 after user information 120 isvalidated.

Step 712 executes by submitting claim code 117 and authentication token616 to cloud-based server 110. In some embodiments, browser 119 maysubmit these items along with user information 120. In otherembodiments, browser 119 may submit these items when requested bycloud-based server 110. Step 714 executes by assigning claim code 117 tothe user. Further, authentication token 616 may be assigned to thesession between the user and the server. The user may print to printingdevice 104 from cloud-based server 110 during the session. Claim code117 also is used to retrieve scanned document 113.

Step 716 executes by ending the session. Step 718 executes by deletingauthentication token 616 from cloud-based server 110 and, if applicable,from browser 119. To initiate a new session to access a scanneddocument, the user will need to login again using the disclosedembodiments. Thus, a new authentication token will be generated at thattime. A determination may be made to delete authentication token 616depending on the content of the token. Further, deletion ofauthentication tokens may depend on the architecture of system 100 andcloud-based server 110. In some embodiments, authentication token 616may not be stored on cloud-based server 100 and, therefore, will notneed to be deleted.

If tokens are stored on cloud-based server 110, then step 718 may needto be executed. If authentication token 616 is a random string, then itshould be stored in database 118 of cloud-based server 110. When arequest comes with authentication token 616, cloud-based server 110makes a database lookup to see if such a token exists. Cloud-basedserver 110 may determine properties within authentication token 616,such as expiry or expiration date/time, ownership, when submitted, andthe like. Cloud-based server 110 may make the database read for everyclient call. This approach may not be suitable for systems havingmultiple independent servers, such as in a distributed system.

In some embodiments, authentication token 616 is encrypted and containsimportant properties that become readable when decrypted. One of thetoken properties may be the expiry timestamp. In these embodiments,cloud-based server 110 only need to decrypt authentication token 616 tocheck its validity. No database read by cloud-based server 110 isneeded. This approach may be faster than the one using a storedauthentication token 616 in database 118. Authentication token 616becomes invalid when it expires, such as within an hour or less. Thus,step 712 may execute by determining whether authentication token 616expired when it is received by cloud-based server 110.

The disclosed embodiments include processes to submit a scanned documentto a cloud-based server, authenticate the user for accessing the scanneddocument, and claim the print job later for printing or otheroperations. The claim code issued in the processes claims the scanneddocument job and is not associated with the user upon generation. Mostapplications authenticate the user then perform print processing.Printing operations are stopped to wait for authentication. A portmonitor may not be able to authenticate and stops printing operations.The disclosed embodiments avoid such delay and inefficient use ofprinting resources by letting the printing process proceed withoutinterruption.

Authentication may be done on a website associated with the cloud-basedserver. Authentication is not done on the port monitor. Further, theport monitor does not need a user interface to authenticate the user. Itis done elsewhere, such as a browser, application, GUI on a mobiledevice, and the like.

As will be appreciated by one skilled in the art, the present inventionmay be embodied as a system, method or computer program product.Accordingly, the present invention may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present invention may take the form of a computer program productembodied in any tangible medium of expression having computer-usableprogram code embodied in the medium.

Any combination of one or more computer usable or computer readablemedium(s) may be utilized. The computer-usable or computer-readablemedium may be, for example but not limited to, an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system, apparatus,device, or propagation medium. More specific examples (a non-exhaustivelist) of the computer-readable medium would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CD-ROM), an optical storage device, a transmission media such as thosesupporting the Internet or an intranet, or a magnetic storage device.Note that the computer-usable or computer-readable medium could even bepaper or another suitable medium upon which the program is printed, asthe program can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory.

Computer program code for carrying out operations of the presentinvention may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava, Smalltalk, C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The program code may execute entirely on the user's computer,partly on the user's computer, as a stand-alone software package, partlyon the user's computer and partly on a remote computer or entirely onthe remote computer or server. In the latter scenario, the remotecomputer may be connected to the user's computer through any type ofnetwork, including a local area network (LAN) or a wide area network(WAN), or the connection may be made to an external computer (forexample, through the Internet using an Internet Service Provider).

The present invention is described with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products according to embodiments of the invention. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce amachine, such that the instructions, which execute via the processor ofthe computer or other programmable data processing apparatus, createmeans for implementing the functions/acts specified in the flowchartand/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an” and “the” are intended toinclude plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specific thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

Embodiments may be implemented as a computer process, a computing systemor as an article of manufacture such as a computer program product ofcomputer readable media. The computer program product may be a computerstorage medium readable by a computer system and encoding a computerprogram instructions for executing a computer process. When accessed,the instructions cause a processor to enable other components to performthe functions disclosed above.

The corresponding structures, material, acts, and equivalents of allmeans or steps plus function elements in the claims below are intendedto include any structure, material or act for performing the function incombination with other claimed elements are specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill without departingfrom the scope and spirit of the invention. The embodiment was chosenand described in order to best explain the principles of the inventionand the practical application, and to enable others of ordinary skill inthe art to understand the invention for embodiments with variousmodifications as are suited to the particular use contemplated.

One or more portions of the disclosed networks or systems may bedistributed across one or more multi-functional printer (MFP) systemscoupled to a network capable of exchanging information and data. Variousfunctions and components of the MFP system may be distributed acrossmultiple client computer platforms, or configured to perform tasks aspart of a distributed system. These components may be executable,intermediate or interpreted code that communicates over the networkusing a protocol. The components may have specified addresses or otherdesignators to identify the components within the network.

It will be apparent to those skilled in the art that variousmodifications to the disclosed may be made without departing from thespirit or scope of the invention. Thus, it is intended that the presentinvention covers the modifications and variations disclosed aboveprovided that these changes come within the scope of the claims andtheir equivalents.

What is claimed is:
 1. A method for authenticating user access to ascanned document at a cloud-based server, the method comprising:scanning a document at a device on a network; uploading data for thescanned document to the cloud-based server from a port monitor;generating a claim code by the cloud-based server; providing the claimcode to the port monitor; launching a browser with a uniform resourcelocator (URL) address indicating the cloud-based server, wherein the URLaddress includes the claim code; assigning the claim code to a usersession initiated by the browser; and selecting the scanned document inthe session associated with the claim code to be sent from thecloud-based server.
 2. The method of claim 1, further comprisinginitiating a redirection from the port monitor to launch the browser. 3.The method of claim 1, wherein the uploading includes streaming the datafor the scanned document to the cloud-based server.
 4. The method ofclaim 1, wherein the uploading includes buffering the data for thescanned document at the device then uploading the buffered job data tothe cloud-based server.
 5. The method of claim 1, wherein the uploadingincludes buffering the job data for the scanned document at thecloud-based server.
 6. The method of claim 1, further comprisingreceiving a unique access URL at the port monitor, wherein the uniqueaccess URL corresponds to the scanned document received at thecloud-based server.
 7. The method of claim 6, further comprising callingthe cloud-based server by the port monitor using the unique access URL.8. The method of claim 7, further comprising submitting documentmetadata information for the scanned document using the unique accessURL.
 9. The method of claim 8, further comprising initiating generationof the claim code at the cloud-based server using the document metadatainformation.
 10. A method for authenticating user access to a scanneddocument at a cloud-based server, the method comprising: uploading datafor the scanned document to the cloud-based server; receiving a firstuniform resource locator (URL) address at a port monitor, wherein thefirst URL address refers the scanned document stored on the cloud-basedserver; submitting a request to access the scanned document using thefirst URL address, wherein the request includes document metadatainformation for the scanned document; generating a claim code for thescanned document at the cloud-based server; receiving the claim code atthe port monitor; forwarding the claim code to the cloud-based serverusing a second URL address; authenticating a user session to access thescanned document according to the claim code; and forwarding the scanneddocument to a device from the cloud-based server.
 11. The method ofclaim 10, further comprising storing the claim code at the cloud-basedserver.
 12. The method of claim 11, further comprising deleting theclaim code from the cloud-based server according to a condition.
 13. Themethod of claim 10, wherein the uploading includes uploading the datafor the scanned document directly to the cloud-based server.
 14. Themethod of claim 10, wherein the uploading includes buffering the datafor the scanned document before uploading to the cloud-based server. 15.The method of claim 10, further comprising embedding the claim code inthe second URL address.
 16. A method for authenticating a user sessionto access a scanned document on a cloud-based server, the methodcomprising: uploading data for the scanned document to the cloud-basedserver using a port monitor; submitting the scanned document includingdocument information metadata from the port monitor, wherein the dataand document information metadata for the scanned document is stored onthe cloud-based server; generating a claim code at the cloud-basedserver; providing the claim code to the port monitor; forwarding theclaim code using a uniform resource locator (URL) address initiated in abrowser by the port monitor to the cloud-based server; determiningwhether user information associated with the claim code is valid;establishing the user session once the user information is validated;and selecting the scanned document on the cloud-based server.
 17. Themethod of claim 16, further comprising sending the scanned document to adevice from the cloud-based server.
 18. The method of claim 16, whereindetermining whether the claim code is valid includes determining, usingthe cloud-based server, that the claim code exists along with the data.19. The method of claim 16, further comprising generating anauthentication token by the cloud-based server upon receipt of the claimcode in the URL address.
 20. The method of claim 19, further comprisingreceiving the authentication token and the claim code at the cloud-basedserver.